Skip to content

docs: add naming conventions for entities#2794

Merged
ucatbas merged 1 commit intomasterfrom
omer/entity-naming-rules
Feb 23, 2026
Merged

docs: add naming conventions for entities#2794
ucatbas merged 1 commit intomasterfrom
omer/entity-naming-rules

Conversation

@omer-topal
Copy link
Copy Markdown
Contributor

@omer-topal omer-topal commented Feb 20, 2026

Summary by CodeRabbit

  • Documentation
    • Clarified and documented explicit entity naming constraints in the Getting Started guide: entity names may only contain letters and underscores, with a maximum of 64 characters.
    • Reorganized the Getting Started documentation's introductory section to better separate entity naming requirements from practical usage examples.

@omer-topal omer-topal requested a review from ucatbas February 20, 2026 09:12
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 20, 2026

📝 Walkthrough

Walkthrough

Documentation updated to explicitly define entity naming constraints: names must contain only letters and underscores with a maximum length of 64 characters. The introductory guidance was reordered to separate naming rules from usage examples.

Changes

Cohort / File(s) Summary
Entity Naming Documentation
docs/getting-started/modeling.mdx
Added explicit constraints for entity names (letters and underscores only, max 64 characters) and restructured sentence ordering to clarify naming rules separately from example usage.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A naming tale, both clear and bright,
Letters dance with underscores' delight,
No sixty-four plus letters may stand,
Documentation guides with careful hand,
Rules refined, the path now clear! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add naming conventions for entities' directly matches the main change, which introduces explicit naming constraints for entity names in documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch omer/entity-naming-rules

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/getting-started/modeling.mdx`:
- Line 63: Remove the trailing whitespace at the end of the sentence "Entity
names may contain only letters and underscores and must be at most 64 characters
long." in the docs text (the sentence shown in the diff) by deleting the extra
space after the final period so the line ends cleanly with the period.

Think of entities as tables in your database. It is strongly recommended to name entities the same as the corresponding database table name. Doing so allows you to model and reason about your authorization and eliminate the possibility of error.

You can create entities using the `entity` keyword. Let's create some entities for our example GitHub authorization logic.
You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Trailing whitespace at the end of Line 63.

The sentence ends with ...64 characters long. (note the space after the period). This is a minor formatting nit.

✏️ Proposed fix
-You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long. 
+You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long.
You can create entities using the `entity` keyword. Entity names may contain only letters and underscores and must be at most 64 characters long.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/getting-started/modeling.mdx` at line 63, Remove the trailing whitespace
at the end of the sentence "Entity names may contain only letters and
underscores and must be at most 64 characters long." in the docs text (the
sentence shown in the diff) by deleting the extra space after the final period
so the line ends cleanly with the period.

@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.63%. Comparing base (e9c0bd1) to head (0f39397).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2794      +/-   ##
==========================================
- Coverage   82.64%   82.63%   -0.01%     
==========================================
  Files          74       74              
  Lines        8125     8125              
==========================================
- Hits         6714     6713       -1     
- Misses        892      893       +1     
  Partials      519      519              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ucatbas ucatbas merged commit c139f98 into master Feb 23, 2026
15 checks passed
@ucatbas ucatbas deleted the omer/entity-naming-rules branch February 23, 2026 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants